Page History: MarketData Request
Compare Page Revisions
Page Revision: 2012/10/16 17:27
Subscribing to Streaming DataThe T4 FIX API provides (optional) subscriptions to streaming market data for all markets available in order routing. Market data is made available asynchronously and concurrently to order routing flow. The market data subscriptions are active during a FIX Session. They are initiated by Market Data Request messages (Tag 35=V). A Market Data Request is a general request for streaming of market data quotes on specific securities. Under the T4 FIX API, securities are defined by the Exchange, Contracts within an exchange and Markets for a specific contract. Exchanges are identified by an unique Exchange ID in Tag 207 (SecurityExchange). Contracts are characterized by its Contract ID in Tag 55 (Symbol). Markets are identified by an unique Market ID by Tag 48 (SecurityID).
Any time during a FIX Session, market data subscriptions can be requested for a specific market by specifying a Subscription Request Type (Tag 263=1). During the FIX session, the streaming market data (for any specific security) can be also unsubscribed (Tag 263=2).
A successful Market Data Request (for subscription) returns one or more Market Data messages containing one or more Market Data Entries. Currently, The T4 FIX API provides market updates with the
MarketData Snapshot message (Tag 35=W). Market Data Snapshots carry multiple blocks of quote data delineated by Market Data Entries. Each Market Data Entry is a bid, an offer, a trade, the opening, closing, or settlement price of a security, the value of an index, the trading session high price, low price, or trade volume, open interest and low and high price limits. Market Data Entries usually have a price and a quantity (size) at a book level (for securities with market depth). For example, in an order book environment, requesting just the top of book would result in two active Market Data Entries; one for the best bid and one for the best offer. For a full book, the bid and offer sides may each have several Market Data Entries corresponding to multiple book levels.
Market Data requests that cannot be honored are notified via the
MarketData Request Reject message.
Subscription TypesThe following Subscription Request Types control attributes, initiation and termination of streaming market data:
Subscribe: A Snapshot + Updates subscription (Tag 263=1) causes the current state of the market to be sent, and any updates as they occur, until the client requests that the Snapshot + Updates be unsubscribed.
When Snapshot + Updates is requested, updates may be full or incremental:
Full Refresh: This mode is optimized to trade off increased bandwidth for simplicity in processing and is intended for requests on only a few instruments. Each FIX Market Data message (in response to a market data subscription request) will contain the complete data requested for one instrument.
Incremental Refresh:
Incremental Refresh mode is not currently implemented in the T4 FIX API. All incremental refreshes are currently sent as
MarketData Snapshots. The Incremental Refresh mode is optimized for handling requests for many instruments while conserving bandwidth. Each Market Data Entry is assigned an MDEntryID unique among all other active entries and incremental update operations (e.g. add, delete and change) can be included in one Incrementatl Refresh message.
UnSubscribe: Unsubscribing from currently streaming market data is specified with an "Unsubscribe" Subscription Request Type (Tag 263=2).
SnapShot: A Market Data Snapshot (Tag 263=0) causes the current state of the market to be sent. Currently, this subscription type is equivalent to Snapshot + Updates (Tag 263=1). Note that as the current data flow is driven by Market Data Snapshot messages, the complete view of a market may be rendered by a single Market Data Snapshot update. For a complete description of the market, the T4 FIX API also sends a Market Data Snapshot message associated with non-book entries (e.g. Trade Volume, Session high, Session low, etc.).
Data Throughput and Buffering LevelsThe T4 FIX API offers several levels of data throughput. The market data subscriber can control the number of quotes and the throughput rate (received by a client application). The T4 FIX API buffers streaming market data flow and dessiminates quotes at the level requested by the API client. The following T4 buffering levels are available:
0. Full Refresh: Same as Smart Buffering.
1. Incremental Refresh: Same as Smart Buffering.
2. SlowTrade: Same as SlowSmart buffering plus every individual trade is received as well. It should be used sparingly due to high bandwidth and potentially large number of messages being received during busy market periods.
3. SmartTrade: Same as Smart buffering plus every individual trade is received as well. It should be used sparingly due to high bandwidth and potentially large number of messages being received during busy market.
4. SlowSmart: Slowed down version of Smart buffering for lower bandwidth usage. This produces depth updates about once per second per market if changes have occurred.
5. Smart: Smart buffering, depth is sent out on different buffering intervals dependent on what has changed in the depth. Changes to the best bid, offer or last trade are sent out frequently, changes that are off the market are sent out less frequently.
6. FastSmart: Faster version of Smart buffering. It sends out changes to best bid or offer prices more frequently. Much higher bandwidth usage.
7. All: All depth updates, no buffering. Not supported by API applications. Specifying this subscription level in the API will result in Smart buffering level. Same as FastSmart buffering plus every individual trade is received as well. It should be used sparingly due to high bandwidth and potentially large number of messages being received during busy market periods.
8. FastTrade: Same as FastSmart buffering plus every individual trade is received as well. It should be used sparingly due to high bandwidth and potentially large number of messages being recieved during busy market periods.
9. TradeOnly: Every individual trade is received, but nothing else - no depth, settlement, highlow, price limits etc.
Book DepthThe T4 FIX API Book Depth controls the number of book levels received for each update. Dependent on the specific security, up to a maximum of 10 book levels are available. The number of levels in the market data book is requested with MarketDepth (Tag 264). Higher number of levels will result in increased bandwidth requirements. If the best bid/offer is just needed for a quote board, a subscription to Level 1 is recommended. If a market is to show all depth lines, subscription to a Market Depth of 10 is required. Even if such security does not support 10 levels of market data, the T4 FIX API will provide the maximum number of levels that security currently supports.
Message Dictionary
| Tag | Field Name | Req'd | Comments |
|---|
| Standard Header | Y | MsgType = V |
| 262 | MDReqID | Y | Must be unique. In order to unsubscribe, it may pertain to the MDReqID of a previous (subscription) Market Data Request. |
| 263 | SubscriptionRequestType | Y | SubscriptionRequestType indicates to the other party what type of response is expected. A snapshot request only asks for current information. A subscribe request asks for updates as the status changes. Unsubscribe will cancel any future update messages from the counter party. Valid values are: |
| | | 0 = SNAPSHOT |
| | | 1 = SUBSCRIBE: Enable Snapshot + Updates |
| | | 2 = UNSUBSCRIBE: Disable previous Snapshot + Update Request |
| 264 | MarketDepth | Y | Requested Depth of market for Subscription or Snapshot. T4 currently supports up to a maximum of 10 levels for selected markets. TopOfBookOnly = 1. FullBook = 10. |
| 265 | MDUpdateType | N | Specifies the type of Market Data throughput (buffering). Valid values are: |
| | | 0 = Full Refresh. Equivalent to T4 Smart. |
| | | 1 = Incremental Refresh. Equivalent to T4 Smart. |
| | | 2 = T4 Slow Trade |
| | | 3 = T4 Smart Trade |
| | | 4 = T4 Slow Smart |
| | | 5 = T4 Smart |
| | | 6 = T4 Fast Smart |
| | | 7 = T4 All |
| | | 8 = T4 Fast Trade |
| | | 9 = T4 Trade Only |
| | Start Repeating Group | |
| 267 | NoMDEntryTypes | Y | Number of MDEntryType fields requested. Repeating Group. |
| 269 | MDEntryType | Y | This is a list of interested Market Data Entries. Must be the first field in this repeating group. Valid values are: |
| | | 0 = Bid |
| | | 1 = Offer |
| | | 2 = Implied Bid |
| | | 3 = Implied Offer |
| | | 4 = Last Trade |
| | | 6 = Settlement |
| | | 7 = Session High |
| | | 8 = Session Low |
| | | K = Price High Limit |
| | | L = Price Low Limit |
| | | B = Trade Volume |
| | End Repeating Group | |
| | Start Repeating Group | |
| 146 | NoRelatedSym | Y | Number of symbols (instruments) requested. Repeating Group. |
| 55 | Symbol | Y | Symbol. Must be the first field in this repeating group. This is the T4 Contract ID. |
| 48 | SecurityID | Y | Security identifier. This is the T4 Market ID. |
| 167 | SecurityType | Y | Instrument type. Futures="FUT", Options="OPT", Stock="STK", Synthetic="SYN", Binary Option="BIN" |
| 207 | SecurityExchange | Y | Can be used to identify the security. This is the T4 Exchange ID. |
| 201 | PutOrCall | N | For Options. Indicates whether an Option is for a put or call. Valid values are: |
| | | 0 = Put |
| | | 1 = Call |
| | End Repeating Group | |
| 1070 | QuoteType | N | Pricing Scheme for Quotes. Valid values are: |
| | | 1 = Ticks |
| | | 2 = Decimal |
| | Standard Trailer | Y |
Sample MessagesSubscribe to streaming data from a specific market
>> 10/10/2012 9:37:58 AM [FIXMARKETDATAREQUEST] 34=1891|49=T4Example|56=T4|52=20121010-14:37:58.720|262=md-10/10/2012 9:37:58 AM|263=1|264=10|265=5|1070=1|267=3|269=0|269=1|269=2|146=1|55=ES|48=CME_20121200_ESZ2|167=FUT|207=CME_Eq|
[FIXMARKETDATAREQUEST]
[MsgSeqNum] 34 = 1891
[SenderCompID] 49 = T4Example
[TargetCompID] 56 = T4
[SendingTime] 52 = 20121010-14:37:58.720
[MDReqID] 262 = md-10/10/2012 9:37:58 AM
[SubscriptionRequestType] 263 = 1 (SNAPSHOT_PLUS_UPDATES)
[MarketDepth] 264 = 10
[MDUpdateType] 265 = 5 (SMART)
[MDQuoteType] 1070 = 1 (TICKS)
[NoMDEntryTypes] 267 = 3
[MDEntryType] 269 = 0 (BID)
[MDEntryType] 269 = 1 (OFFER)
[MDEntryType] 269 = 2 (IMPLIED_BID)
[NoRelatedSym] 146 = 1
[Symbol] 55 = ES
[SecurityID] 48 = CME_20121200_ESZ2
[SecurityType] 167 = FUT (FUTURE)
[SecurityExchange] 207 = CME_Eq
UnSubscribe from a currently streaming market
>> 10/10/2012 9:37:59 AM [FIXMARKETDATAREQUEST] 34=1892|49=T4Example|56=T4|52=20121010-14:37:59.765|262=md-10/10/2012 9:37:59 AM|263=2|264=10|265=5|1070=1|267=3|269=0|269=1|269=2|146=1|55=ES|48=CME_20121200_ESZ2|167=FUT|207=CME_Eq|
[FIXMARKETDATAREQUEST]
[MsgSeqNum] 34 = 1892
[SenderCompID] 49 = T4Example
[TargetCompID] 56 = T4
[SendingTime] 52 = 20121010-14:37:59.765
[MDReqID] 262 = md-10/10/2012 9:37:59 AM
[SubscriptionRequestType] 263 = 2 (DISABLE_PREVIOUS_SNAPSHOT_PLUS_UPDATE_REQUEST)
[MarketDepth] 264 = 10
[MDUpdateType] 265 = 5 (SMART)
[MDQuoteType] 1070 = 1 (TICKS)
[NoMDEntryTypes] 267 = 3
[MDEntryType] 269 = 0 (BID)
[MDEntryType] 269 = 1 (OFFER)
[MDEntryType] 269 = 2 (IMPLIED_BID)
[NoRelatedSym] 146 = 1
[Symbol] 55 = ES
[SecurityID] 48 = CME_20121200_ESZ2
[SecurityType] 167 = FUT (FUTURE)
[SecurityExchange] 207 = CME_Eq
FIX API Home Page.